Pain point to solve:
On PtSituationElement level one can define multiple ValidityPeriods (onbound). However, on Consequence or PassengerInformationAction level one cannot distinguish between these periods! On Consequence level this is solved by providing a corresponding element "Period" that overwrites the top level periods if one has to distinguish. However, on action level no such element exists.

• Alternatively, extend ValidityPeriod element on PtSituationElement level by an “id” so that each period may be referenced on action level.
• Multiple ValidityPeriods might for example be necessary in case of road works that only affects pt objects periodically during the night.
• Also, similar to how Interval on PushedActionStructure level supposedly works, a period (reference) on action level would enable a producer to publish some textual content via journey planner (Perspective ‘whilePlanningTrip’) before the situation actually affects the pt objects. This is not possible with PublicationWindow alone (which is independent from the ValidityPeriods). The only option here is to extend the ValidityPeriod which is certainly not desired for other Perspectives than 'whilePlanningTrip'.

A similar proposal was already discussed extensively within the SG7 group, but multiple counter proposals were suggested instead. These were all discussed within the UmS group (german speaking SX profile VDV736 that conceived the PassengerInformationActionStructure) but unfortunately were not able to solve the issues at hand.